Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

tests/core/config/env-interpolator.test.js (1)

14-21: 🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win

Relative import — use an absolute module specifier.

The path.resolve(__dirname, ...) + path.join(...) construction is still a relative import in disguise and violates the project's coding standards.

As per coding guidelines, "Use absolute imports instead of relative imports in all code" for **/*.{js,jsx,ts,tsx} files.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/core/config/env-interpolator.test.js` around lines 14 - 21, The test
uses a relative-import workaround (path.resolve(__dirname, ...) +
path.join(...)) to require the module that exports interpolateString,
interpolateEnvVars, lintEnvPatterns, and ENV_VAR_PATTERN; replace that with a
single absolute module specifier require call (e.g.,
require('aiox-core/core/config/env-interpolator') or whatever the project’s
canonical absolute package path is) and keep the existing destructured imports
so the test imports interpolateString, interpolateEnvVars, lintEnvPatterns, and
ENV_VAR_PATTERN via the absolute require instead of constructing a filesystem
path.

tests/core/config/env-interpolator.test.js (2)

204-219: ⚡ Quick win

ENV_VAR_PATTERN global lastIndex can leak across the preceding test runs.

The interpolateString and interpolateEnvVars suites invoke the production functions that internally consume ENV_VAR_PATTERN (a global regex). If the implementation ever exits a exec()-loop early (e.g., error path), lastIndex could be left non-zero. While the tests here correctly use new RegExp(ENV_VAR_PATTERN.source) for their own assertions — so these tests are safe — adding an explicit beforeEach reset prevents any future direct use of ENV_VAR_PATTERN in this block from being order-dependent.

♻️ Proposed safeguard

 describe('ENV_VAR_PATTERN', () => {
+  beforeEach(() => {
+    ENV_VAR_PATTERN.lastIndex = 0;
+  });
+
   it('deve ser uma regex global', () => {

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/core/config/env-interpolator.test.js` around lines 204 - 219, Add a
beforeEach in this describe block that resets the global regex state to avoid
test-order flakiness: explicitly set ENV_VAR_PATTERN.lastIndex = 0 before each
test so that any prior exec() usage by interpolateString or interpolateEnvVars
cannot leak a non-zero lastIndex into these specs; reference the ENV_VAR_PATTERN
identifier and mention the related functions interpolateString and
interpolateEnvVars so maintainers know why the reset is needed.

---

28-36: ⚡ Quick win

process.env isolation should use afterEach, not afterAll.

Both describe blocks restore process.env only in afterAll. If a test throws unexpectedly (rather than an assertion failure), the remaining tests in that block still receive a reset env via beforeEach, but any parallelized or cross-describe side effects accumulate until the entire suite for that block finishes. Replacing afterAll with afterEach makes the cleanup symmetric with beforeEach and removes any ambiguity.

♻️ Proposed fix (applies to both describe blocks at lines 34–36 and 90–92)

-  afterAll(() => {
+  afterEach(() => {
     process.env = ORIGINAL_ENV;
   });

Also applies to: 84-92

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/core/config/env-interpolator.test.js` around lines 28 - 36, The test
restores process.env in an afterAll but the setup uses beforeEach, so switch the
teardown to afterEach to ensure isolation per-test; update the two occurrences
of afterAll (() => { process.env = ORIGINAL_ENV; }) to afterEach (() => {
process.env = ORIGINAL_ENV; }) in the env-interpolator.test.js file so the
beforeEach/afterEach pair correctly reset process.env for each test (apply to
both describe blocks that reference ORIGINAL_ENV, beforeEach, and afterAll).